CGI Test Cases (Windows version)

This document contains a number of trivial examples of CGI usage. It requires access via a server, not in local file mode. Also, you must be using a browser that supports HTML forms.

If you are currently reading in local file mode, start your server now, then click here to switch to client-server mode. This same document might appear shortly...

If you made it this far, you're ready to try the scripts. Strictly speaking, it wouldn't have been necessary to switch to client-server mode, the URLs for the script examples would make the connection via the network even from local file mode. However, I wanted to make sure you had your server running and were able to communicate with it. If you are interested, you should look at the source for the CGI script used in these examples.

For more source of CGI scripts, see the CGI archive of scripts people have written. In addition, see the NCSA httpd distribution in the cgi-src directory.

This is just a request for a CGI script with no extra path information and no query.

http://yourhost/cgi-bin/test-cgi.bat

This is a request for a script with extra path information, and no query.

http://yourhost/cgi-bin/test-cgi.bat/extra/path

This is a request for a script with no extra path information, and an ISINDEX query.

http://yourhost/cgi-bin/test-cgi.bat?query

This is a request for a script with extra path information as well as an ISINDEX query.

http://yourhost/cgi-bin/test-cgi.bat/extra/path?a+query

You'll need a browser which supports HTML forms for this example. Clicking the submit button will send an form request with no extra path information using the GET method.

You'll need a browser which supports HTML forms for this example. Clicking the submit button will send an form request with no extra path information using the POST method.

You'll need a browser which supports HTML forms for this example. Clicking the submit button will send an form request with extra path information of /foo using the POST method.

Return to the overview

Robert B. Denny <rdenny@netcom.com>